Title: Squads


Squad Members


Body of Ownership:

Sales Goals - Activities Dashboard - Marketplace -  iPaaS - Lead Scoring - Tags - Invoicing integration - Esignature integration - Freshdesk integration.


Sprint Summary:


Sprint NameSprint DurationPlanned ItemsCompleted ItemsAd Hoc Items / Unplanned ItemsRetrospectiveStar Performer / Sprint Champion
1
Aquaman

 
-
 


28

20


Aquaman - Retrospective
2
Batman

 
-
 


16

8


Batman - Retrospective
3
Capt. Marvel

 
-
 


27

5 + 10 (DOD reached) = 15


Capt.Marvel - Retrospective
4
Deadpool

 
-
 


25

23 + 2 ( DOD reached) = 25

7

Deadpool Retrospective
5
Elektra

 
-


28
Story Points : 42

29
Story Points : 78

8

Elektra Retrospective
6
Flash

 
-


29
Story Points : 49

22
Story Points : 55

6

Flash Retrospective

Team
7
Groot

 
-


22
Story Points : 43

17
Story Points : 45

5

Groot Retrospective

Team
8
Hulk

 
-


18
Story Points : 62

17
Story Points : 62

5

Hulk Retrospective

Team
9


Iron Man



 
-




19
Story Points : 73



16
Story Points : 67




Iron Man Retrospective
10

Joker


 
-


23
Story Points : 84

24
Story Points : 79

8

Joker Retrospective


Gowthaman Ravindran

11

Krypto


 
-


20
Story Points : 77

19
Story Points : 76

8

Krypto Retrospective
12


Loki



 
-



25
Story Points : 79


22
Story Points : 74


11



Loki Retrospective


Hari Bukke
Abishek Kumar S

Special Appreciations
Designer - Gopi Krishna
Reviews and response time

13



Mysterio



 
-




23
Story Points : 101


17
Story Points : 69



8



Mysterio Retrospective


Rubika Srinivasan
Hari Bukke

Special Appreciations
Designer - Gopi Krishna
Reviews and response time

14
Nightwing

 
-

24
Story Points : 100
20
Story Points: 74

5

Nightwing Retrospective
15
Ozymandias

 
-

22
Story Points: 91
17
Story Points : 59

5

16
Punisher

 
-

22
Story Points: 90
19
Story Points : 66

5

17
Quarantine 

 
-

22
Story Points: 76
21
Story Points : 68

5
Quarantine Retrospective
18
Red Skull

 
-

16
Story Points: 50
11
Story Points : 25

9
Red Skull Retrospective
  • Planned Items - Defines the number of items(User story, Task, Bugs) committed by all folks during the sprint planning.
  • Ad Hoc Items - Defines the numbers of items (User story, Task, Bugs) added to the ongoing sprint on priority.
  • Completed Items -  Defines the numbers of items (User story, Task, Bugs) completed in the sprint but the count does not include the Ad-hoc and unplanned Items
  • Unplanned Items - Defined the number of items (User story, Task, Bugs) added after the beginning of the sprint but not part of the original sprint plan.
  • DOD - Definition of Done , should be added to the ticket as comment or description on what the status of the ticket should be by the end of the sprint.













Slogan of the Squad : Hakkuna Mattata

Squad Members

Engineering Manager: Mohaan Raja 

TPM: Ravi Sankar 

Architects:

BE - Sivalingam Selvasekaran 

FE - Harish Sundararaman 

Backend:

Prakash Thiyagarajan

Chavitipalli Raju 

Haiden Arulappan 

Gopal 

Poornima Anantharaman 

Surendar Dillibabu 

Frontend:

Sampath Kumar Paravasthu 

Triveniprasad gupta 

QA:

Senthil Palanisamy 

Deepak Jayaram 

kanishkar Uthayasuriyan 


Hacker Hostel 2.0 - Body of ownership

  1. Trinity(Contacts integration),
  2. Google calendar integration,
  3. Outlook calendar integration,
  4. Tasks,
  5. Slack/Connect,
  6. Appointments,
  7. Sales activities,
  8. Notes,
  9. Notifications,
  10. Tags,
  11. Attachments,
  12. Files,
  13. Web forms


Hacker Hostel Testplans


Squad Details

Squad Name
BoOE-signature integration, CPQ, Documents, Docusign, invoicing integration

Platform: Marketplace
EMDipender Singh 
BE
FE
SET
BE-ArchitectGangadharan Krishnamoorthy 
FE-ArchitectUmashankar Masilamani 
Product Management 
Program ManagerRamya Raghavan 
TPMSavithri Ganesan 

Retro Template 

Body of Ownership

Core Objects (Lead/Contact/Account/Deal)
Multi-currency
Data Import/Export
External Migrations
Trinity
Filters

Team Members:


Arya Stark Retrospective

Black Eye Retrospective

Bran Stark Retrospective

Definition of DONE

Definition of READY

L2 Resolution Document

FWCRM SSO LIMITATIONS:

Sample support ticketIssueDebugging
https://freshsalesdev.freshdesk.com/a/tickets/7465
  • Unable to create deals, it shows error message "Failed to create opportunity, deal type invalid format", 

PiedPiper Testplan

PP - Annamalai Retrospective

PP - Baasha Retrospective

PP - Chandramukhi Retrospective

PP - Jhonny Retrospective

PP - Kabali Retrospective

PP - Little Sombrero Retrospective

PP-Malin Retrospective

PP - Pinwheel Retrospective

PP - Sculptor Retrospective

PP - Tadpole Retrospective

PP - Triangulum Retrospective

PP - Whirlpool Retrospective

RCA Analysis:

1.  Account Timezone during Import

Impact:

The issue was in Staging Impact time: Blocked deployment for a day

Retrospective Action Items - PiedPiper

QuarterSprintAction ItemOwnerETAStatusMeasurement Criteria (if any)
Q1-2021Contractor NesamaniHaving a consolidated 6pm resolution time for every L2

 


We see some tickets reopened(which are closed earlier or couple of days before) around 7pm on friday and we have the SLA breached by then.

Sprint Retrospectives

Sprint 20190911 Retrospective

What did we do well?

  • In general went well
  • Clear priority
  • Team adapted to the sprint ceremonies
  • Committed was delivered to an extent
  • More freedom
  • More user story clarity for the team
  • PM - Team interaction improved
  • Grooming went well
  • Daily standups
  • Sprint 1 goals achieved (ceremonies and objectives met)
  • NO fights!!!
  • Open conversation

What should we have done better?

  • Tickets were not updated on-time
  • Previous responsibilities should have been identified and planned
  • Proper estimates 
  • Commitments were high
  • Unplanned items were picked
  • Work better as a team 
  • Estimates are not proper because of missed details 
  • Tickets are missing details 
  • Impact areas were missed
  • Lack of transparency (sprint board and tickets were bare)
  • Some active tickets missing in board
  • Mid sprint prioritisation missing
  • Actively pick from Ready-for-Dev was missing

Sprint 20190925 Retrospective

What did we do well?

  • Shipped Custom modules import
  • Nearly done with Custom modules import UI automations
  • Landing page customisation most of what was planned completed

What should we have done better?

  • Backlog grooming should be done more aggressively (Missed a critical piece during initial discussions) 
  • Tickets to be updated more religiously

Sprint 20191009 Retrospective

What did we do well?

  • We got better at sprint planning and estimates
  • Freshrelease tickets updates have improved
  • Were able to adapt to urgent requests

What should we have done better?

  • Feature mocks should have been frozen (Landing page customisation)
  • Time/bandwidth allocated for L2 is lesser than needed
  • Collate the frequent L2 tasks and empower the support team to resolve themselves
  • Tickets for testing piles up
  • Estimation to improve
  • Availability estimates to improve (external team dependencies to be considered)
  • Unplanned items are increasing
  • Tickets lack updates (comments informing of progress)
  • Blockers were not called out during standup
  • All work items were not captured in sprint

Sprint 20200115 Retrospective

What did we do well?

What should we have done better?

  • Act with urgency in Filter UX enhancement . Delivered the feature on committed timeline +1
  • Collaboration with PM and Design team . Helps the team to deliver the feature on time- +2
  • Realistic sprint planning 
  • Responded L2 support tickets within SLA 
  • Time Entires for resolving L2 tickets helps the team to track the time taken to responding the tickets.Helps in story estimation
  • On Sales 360 item - Impact analysis before starting dev work helps the team to identifying the issues/blockers earlier +2
  • Collaboration with PM team . Get everything cleared before starting the story
  • No unplanned items 
  • Good communication within team
  • Sprint Planning - Allocating single dev for L2 , Rspec  , Prod lights-on activity
  • Impact Analysis should be improved, we missed few bugs on existing filter UX -Filter UX enhancements
  • Blocked below ticket even after the implementation and testing is done because of tech implementation https://freshworks.freshrelease.com/FSALES/issues/FSALES-17103 . Review the tech implementation before dev starting.
  • Planning for RSPEC and Automation coverage 
  • Update the acceptance criteria based on stands taken, instead on tracking comments
  • Act with urgency for all tickets 
  • Sales 360:
    • Need mocks before starting Development
    • Unanswered / unresolved question before ready for dev
Appreciations

Action Items:

Sprint 20200211 Retrospective

What did we do well ?What should we have done better?
  • Shift Left testing approach . Finding Impact areas by QA in development phase(before testing) , helps the developer to covers missed areas in development phase. 
  • Communication among the team .Sales 360 standup helps the team to conveys their daily status progress and blockers if they are facing . Resolving blockers within sales 360 standup helps the team to move fast forward.
  • Timeline for each tickets is clearly mentioned
  • Team taking ownership on assigned task, delivering them on committed timeline
  • Actual work is progressing
  • Sticking to the scope of the ticket -For feature Label renaming(Lead score to score and owner) we have adding the scope of the ticket while ticket is testing 
  • Temp feature check should have been implemented in prior .  Developer reworking on existing code they have committed to accommodated the changes (in both backend and frontend) . +2
  • Planning items in-prior to sprint planning not in the middle of the spint . 
  • Ticket Updation - Adding work progress , updating acceptance criteria and stand/decision taken.
  • Sales 360 standup is high level status update . so we will continue to have daily squad standup to get updates.

Appreciations

  • Meenakshi +3 - Sharing impacted areas to developers before the ticket is Ready for QA .

Action Items:

→ Freshrelease ticket updation - For update in acceptance criteria and Decision/Stands taken  . 

→ Setup calendar-Informing planned leaves to the team 


Sprint 20200225 Retrospective

What did we do well ?

What should we have done better?

  • Communication among team for calling out and resolving issues +1
  • Act with urgency and commitments towards work on sales 360 items +1
  • Onboarding the new comers to the squad
  • QA involvement in finding impact areas and writing test cases before feature in Ready for QA
  • Time spent to work on Reducing automation pipeline
  • Complete integration setup in Docker Environment needs to be there as in staging to test everything before signing off in branch +1
  • Trinity docker is deleted and is not communicated to the team. we figured out while testing .
  • ETA timeline issues - unable to work on SLA Metrics(Adding Rspec/Ember/Automation test cases) for last name optional feature. since we have updated the ETA .
  • Freshchat integration is not be working in dockers and is not communicated to team.

Appreciations

Action Items:

->Integration setup in Docker Environment needs to be there as in staging to test everything before signing off in branch testing - Akshayvaliya Rakkanchath


What did we do well ?

What should we have done better?

  • Squad Rspec percentage got increased (85%) as we assigned Rspec ticket for Tamizhselvan R  in this sprint and achieved 100% coverage on file crm_data_migration_util.rb
  • Abishek in speed mode helps the team to delivered tickets within in the sprint- FSALES-16567,18175,17497.Kudos to Abishek Kumar S
  • Getting import errors logs through mails.Helping team to resolve/getting insights on issues  without depending on others .Thanks for the initiative  Irfan Shaik.+1
  • Irfan and Nivedita is doing initial code review , before send to bhagi . 
  • We picked up unplanned items (7)  and delivered it in sprint.
  • sync between PM before handing over the requirement to Engineering team. i.e , Issue in adding Twitter in group mandatory fields as part of last name feature.+1
  • Past two sprint , we were not doing story grooming . Need to have tickets in hand before doing sprint planning.+1 
  • Proper Estimation and Speed up the development and testing - Last name ,  Subscription type and status feature is spilled over from last 4 sprints.+1 
  • Freshrelease ticket Updation on daily basis
  • Proactive communication on Blockers and Issues and owning the problems/issues.

Appreciations

Action Items:

-


What did we do well ?

What should we have done better?

  • Last name went to production without any issues. Extraordinary work on Last name optional feature as it has major impact in all over areas , we shipped it smoothly . 
  • Working remotely (WFH) is working well
    • Sprint ceremonies are going regular
    • Work Progress happening
    • People are helping each other and responding on time
  • Lack of Backlog tickets and planned pipeline is missing . We should have tickets before sprint planning- +3
  • Full attendance in squad standup . As we are working remotely , we would like to connect with everyone in stand-up and sharing the things.  +2
  • Need to improve the communication - As we are doing WFH, we should be proactive/over communicated when communicating the blockers,asking peers help.
  • Focusing on L2 tickets - As we are occupied with sales 360 items , we are missing SLA on some of L2 tickets.

Appreciations

Action Items:


What did we do well ?

What should we have done better?

  • Tracking the Import Failures/Errors logs in Production environment.We have found two major root causes for the failures and fixed one issue in this sprint.(For reference,FSALES-19895,19705).+3
  • Sprint Planning went well.We allocated two resources for resolving L2 issues . In sprint beginning days , we are having 8 overdue tickets . It helps us to resolve those tickets and maintaining SLAs.+3
  • Related list bug - Tamizh has fixed the bug (https://freshworks.freshrelease.com/FSALES/issues/FSALES-15232) . This task helps him for learning new stuffs in development.
  • Sprint ceremonies went well. Active Participations in daily standups .+2
  • Involving multiple Devs and QA into single Epic(for this sprint  we are having Color changes) and shipping them out .That strategy is working out.
  • Color changes Feature:Communication and Collaboration between team(Designer,Devs,QAs) is going Good. Three squads are working on this item and Playing as a team and resolving the stuffs.+2
  • Subscription Status and Types :
    • Getting requirement changes in the middle of   testing .Many breakages in the impact ares because of changing requirements .
    • QA and Impact areas review can also be checked with other squad QAs to avoid the bug leakages.
  • We were not picking any major item in this sprint apart from subscription types and status and color changes.    
  • Ticket updation with the detailed description in Acceptance criteria and Record the conversation/tech discussion in tickets. It will helps the people to get the progress . +2

Appreciations


What did we do well ?

What should we have done better?

  • Estimation should be better  +2
  • Monitor L2 issues on daily and L2 resolution needs to be faster   +1
  • Need to accept mocks and stands before picking ticket .Acceptance criteria should be signed off before dev started working on this.+1
  • Better haystack logs for debugging L2 and prod issues. 
  • Need to understand impact before starting to test
  • Need to complete all planned items . if story takes time , inform the stakeholders proactively about the extension in ETA.
  • Automation for tickets have to followed up +1
  • Review of PRs need to be followed up
  • Test cases should be written and reviewed before actual testing started

Appreciations

Action ItemOwnerETA
Create Haystack log ticket

 

Update L2 Resolution Document

 

Test cases should be done before start of
testing and should get reviewed 
Meenaloshani Murugan
Automation script work should be tracked in sprintMeenaloshani Murugan


What did we do well ?

What should we have done better?

  • Smooth sprint
  • We have pulled in dev tasks than whole tickets for the tickets that  Definition of Done is Dev completed 
  • Improvement in L2 resolution
  • Sprint Planning went well -+2
    • Tickets were identified/shared before the ceremony
    • Tickets assigned to individuals
  • Sliced epics(timeline feeds, custom for sales 360 GA item) into smaller tickets i.e, Tech implementation, pre-requisite and completing them in this sprints. +2
  • Following up on last sprint action items - Test case reviews is done before actual testing
  • Surface issues in staging to stakeholders +1
  • Identify and test more impact areas
  • Adding existing cases during impact regression 
  • L2 Resolution: 
    • Update agent 
    • Update the comments with the progress info
    • Find the temporary solution/hacks to cool down the customers if the permanent fix is hard and taking time.
    • Pick up tickets on priority
  • Tickets in review state for long time . Individual assignee bring this in standup incase any showstoppers 

Appreciations


Notes:
--


What did we do well ?

What should we have done better?

  • Integrated with team easily
  • Increased automation pass percentage +1
  • Most tickets completed +4
  • Dev collaborations was good
  • Good estimation on tickets - role management
  • Clearly defined DOD on tickets +1
  • Primary and secondary on L2 from QA side
  • L2 SLA breach was less
  • Prepared for retro
  • More clarity on tickets when estimating +1
  • Reduce large unplanned items
  • Huge amount of time spent in discussions for unblocking
  • Mocks to be analysed in depth by dev before picking +2
  • Tickets should be updated more regularly (Freshrelease and Freshdesk) +2
  • Reply to tags in support tickets to unblock +1
  • Proper testing plan for inter team tickets
  • Checking for available test cases during estimation
  • Involve dev and QA during evaluation phase of ticket +1
  • Accounting for test case splitting time during estimation
  • Checking automation available during estimation
  • Ensure all features are ready for merge by the last Monday of sprint

Appreciations

Notes:
--


What did we do well ?

What should we have done better?

  • completed 20 tickets with 55 story points +3
  • Good effort on timelines ticket
  • QA spent more time on in depth test cases +2
  • L2 resolutions 
  • Knowledge on other products improved
  • Test cases written in parallel with dev work
  • PMs involved in standup for quick resolutions
  • Taking ownership on tickets +1
  • Technical stories completed along with sales360 items
  • Good communication with stake holders for timelines and custom roles ticket 
  • Mocks could be made after getting inputs from all products
  • Better use case capturing in the initial stages
  • Assigning L2s before SLA breach +1
  • Ticket estimation can be improved 
  • Daily updates on tickets +1
  • Test case review can be faster
  • Pick up unplanned items on priority from EMs and update in ticket

Appreciations

Notes:
--


What did we do well ?

What should we have done better?

  • Discussing feature blockers/L2 tickets after standup +2
  • L2 addressed on time and no SLA breached ticket in this sprint +2
  • Dev fixing the bugs proactively that helps QA proceed the testing without blockers
  • Bundle signup helps the team to perform integration testing in docker
  • Good work in Timeline feeds ,Custom Roles tickets . Tickets are on track . + 3
  • Collaboration between cross team(FM ,Fchat ,FCaller,MCR) in Integration testing went well +1
  • Dev/QA owner of the ticket is not notified when there is mock change +3
  • Requirement came in at the end of development . Because of this , we are not able to meet the Definition Of Done(Dev complete) of lead management ticket .
  • Bundle signup , Docker setup for integration testing-Taking time 
  • Documenting the docker set up issues with FAQs will helps others to resolve the issues quickly
  • Mock Delayed -Timeline feeds Entered/Exited journey changes 
  • Estimation needs to be improve when we are planning integration testing .Custom Roles sales360 ,Timeline feeds +2 
  • New finding in testing phase and missing events are not incorporated in timeline feeds ticket . 

Appreciations

Venkat Narayanan completing Lead management UI task .

Bhagirath Goud For implementing bundle signup thing in docker , helping kishore in lead management ticket

Sivasubramanian Ramar Kishore Shanmugam Meenakshi Manikandaswamy Gopal Krishna -Resolving L2 .No SLA breached tic +2

Vijayaragavan Venkatarathinam - For advising the team to discussing L2 after standup.+1

Venkat Narayanan Proactively fixing the bugs 

Nivedita Peddiraju - Taking ownership for timeline feeds ticket . Resolving the docker integration issues in upfront +1

Nivedita Peddiraju Venkat Narayanan Gopal Krishna -Good work and great effort in timeline feeds +3

Irfan Shaik Meenakshi Manikandaswamy -Coordination with cross team , Proactively calling out blockers to stakeholders - +2

Kishore Shanmugam - craftsmanship /quality of work in lead management story . 

Notes:
--


What did we do well ?

What should we have done better?

  • Timeline Feeds went live  +4
  • Resolving L2 on time . No SLA breached ticket . +4
  • Ownership and taking initiative for integration testing i.e, timeline feeds ,custom roles testing. +2
  • Analysing impact area ticket before starting the development of  the ticket
  • communication issue with PMs and other products Dev/QA 's  while doing integration testing .We can form virtual war room to resolve this .
  • PM in daily standup +1
  • Lead Management story :
    • Detailed description of the ticket and freezed requirement document before dev +2
    • Mock changes during the development
    • Delay in mocks for requirement (forecast type) changes that came in the middle of development
  • Reporting the issue to feeder products in common channel and moving head with other works
  • Ticket updation needs to be improve
  • Communicate issues in the channel instead of informing in person
  • Picking tickets without freezed mocks and documents

Appreciations


What did we do well ?

What should we have done better?

  • S360 custom Roles went Production +5
  • Lead management ticket is on track +1 
  • Solving L2 tickets +1
  • Estimation needs to be improved . For s360 user stories where multiple team involved to perform integration testing + 2
  • QAs should involve in feature discussion from the beginning of development+1
  • App-cues : Requirement level discussion should be done before starting the dev work
  • Migration testing needs to be covered both happy path/negative scenarios
  • Stack setting and Docker configure needs to be updated in channel before merging feature to staging .
  • PM review should be done before starting the testing +3
  • Story estimation in grooming,planning still has to be better .
  • writing confluence doc for docker issue .

Appreciations


What did we do well ?

What should we have done better?

  • Lead management is being shipped +6
  • L2 resolving has good progress +2
  • Great coordination even with new stands in ticket
  • Great work in reducing icon size
  • L2 tickets can be reassigned before overdue
  • Dependencies can be identified in early stages
  • Mocks can be frozen before dev +1
  • Large tickets can be broken up into smaller tickets for testing +2
  • Templates and stands can be documented before dev +2
  • Stack setup confluence doc can be prepared +3
  • Estimation can be done better after analysing ticket +2
  • Cache issues and queue issues found only in staging 

Appreciations

Action items


What did we do well ?

What should we have done better?

  • Onboarding pushed to staging +5
  • No L2 sla breach +2
  • Latest stand updation in tickets +1
  • New interns
  • Closed adhoc tickets on time +1
  • Better estimates +2
  • Ticket status updation +2
  • Better impact areas for L4 bugs
  • Existing tickets to be revisited on picking adhoc +1
  • Tickets created for items picking mid sprint
  • Trouble shooting cross squads
  • Better splitting of tickets with clear DOD
  • Meetings going for too long
  • Follow up tickets on the action items

Appreciations

Action items

  • PM review in earlier stage of ticket


What did we do well ?

What should we have done better?

  • L2 handling consistently well +3
  • Shipping adhoc items on time +2
  • Sprint story points closed is good +4
  • Writing tech blogs
  • Allocating bandwidth for adhoc items in planning
  • Team members are always available to help out
  • Analysing tech debts better with clearer goal metrics and subtasks
  • Performance tickets with proper data sets and expectations for each task +3
  • Estimation of tickets should be improved +1
  • Time allocated for adhoc GA items can be reduced
  • QA test cases during development 
  • Technical onboarding setup can be solved better
  • Ticket statuses should be updated better

Appreciations

Action Items


What did we do well ?

What should we have done better?

  • Show only empty fields well received +2
  • L2s handled well +3
  • Lead related performance improved by around 50%
  • Shipped more bug fixes
  • Getting huge PR reviewed in small chunks
  • Meetings ending on time
  • Everyone completed most of our tickets
  • Documenting L2 resolutions at a freshsales level
  • Clearer initial analysis of status cross teams
  • Better communication cross teams
  • More info on tickets being groomed - PM and tech discussions
  • L2 dev effort can be revisited
  • DOM level changes during bug fixing and review should be informed to QAs
  • Removing unused code in optimisation tickets
  • L2 secondary could be utilised better

Appreciations

Action Items
  • Write more optimised rspecs that dont impact other cases


What did we do well ?

What should we have done better?

  • L2s were handled well +5
  • Most tickets are completed - 51 story points +5
  • PMs added sufficient info in grooming tickets beforehand
  • Squad performing self sufficiently
  • Dev impact checklist can be added +1
  • Bug fixing estimates can be done better
  • Migration edge cases can be covered better
  • Performance testing should have equal importance in functional cases
  • Test cases to be written before estimating testing
  • L2s handled metrics can be captured

Appreciations

Action Items


What did we do well ?

What should we have done better?

  • Deal management ticket went to prod
  • Onboarding went to prod 
  • L2s handling as a team +2
  • Highest sprint story points covered - 67 +4
  • CRM GA and time sensitive items deployed with urgency +5
  • Developer onboarding doc is thorough
  • Testing estimation for reduce duplicates could be better
  • Dev estimates for onboarding could have been better
  • Docker image with the dev setup ready
  • 3 L2s slipped
  • Need to take more timeoffs
  • Need to reduce bug leakage due to impact misses

Appreciations

Action Items


What did we do well ?

What should we have done better?

  • L2s handled well +4
  • Took up performance tickets +1
  • Better impact area analysis before and after picking for testing +2
  • Better analysis of tickets before pulling in as no testing required
  • Better ticket estimation +1
  • More conscious about the SLA breaching tickets
  • Time spent in setting up stack is more +1
  • More testing and impact areas identified before merging to staging
  • Do a small retro for breached L2s as soon as breached

Appreciations

Action Items
  • Mark 'Regression suite run in branch' field as required before staging merge - Akshayvaliya Rakkanchath
  • Making confluence page for common issues faced (Like rts setup in stack) - Irfan Shaik


What did we do well ?

What should we have done better?

  • No L2s breached SLA +5
  • Great work on reduce duplicates +1
  • Allocate more bandwidth for L2s
  • Better impact areas to be captured during grooming (Both technical and product-wise) +1
  • Add comments in code regarding the reason for code change(Better documentation) +3
  • Revising estimates can be called out earlier +2
  • Adding time for dev testing, unit cases

Appreciations

Action Items


What did we do well ?

What should we have done better?

  • No L2s breached SLA +5
  • Discussing in depth in standups
  • Blockers getting addressed quickly in standups or post them
  • Creating L4s for script ran L2s
  • Import failure tickets were handled
  • Sprint points delivered has gone down +2
  • L2 reassigning can be done earlier +2
  • Sprint estimation and ETA can be better with buffer +1

Appreciations

Action Items


What did we do well ?

What should we have done better?

  • L2 SLA compliance went well +3
  • Good discussions in grooming 
  • CPQ EKS frequent issues can be documented (Migration, logs of cpq, not able to track deployment issues ) +2
  • Better ticket and story points planning +2
  • CRM migration tickets need to be better scoped (The parts to be handled here and ones created as a different ticket)
  • FWCRM L2s are being passed between multiple products

Appreciations

Action Items
  • Follow up on EKS issues with concerned team


What did we do well ?

What should we have done better?

  • Migration tickets are being picked up well and without hiccups+2
  • Squad meetings are happening well
  • SLA resolutions very proactive +1
  • Migration blockers resolved in standups
  • Hackathon full team participation +1
  • 1 L2 SLA breached +1
  • EKS issues still present +3
  • Communication on staging being reopened for commits
  • Better understanding of the ticket scope

Action Items


What did we do well ?

What should we have done better?



Appreciations


Action Items


What did we do well ?

What should we have done better?

  • Migration tickets are going smoothly with blockers resolved +1
  • L2s were handled without breaches +3
  • Blockers are being resolved in daily standups +1
  • Number of L2s reduced but more complex ones surfacing
  • Squad won in 2 categories in Q3 awards
  • More tickets(and story points) can be completed in the sprint +1
  • Reduce functional bugs post release

Appreciations

Action Items


What did we do well?

What should we have done better?

  • L2 SLA compliance +6
  • Sprint tickets - Dev/QA progress going smoothly +3
  • Should try to close the L2s before holidays + 1
  • Automation result verification consumes time
  • Local setup documentation update - Big Sur OS +1

Appreciations

Action Items


What did we do well?

What should we have done better?

  • Approachable team +1
  • Migration tickets are going on track +1
  • Maintaining L2s well
  • Migration tickets planning and calling out blockers
  • Better following up on L2 tickets
  • Freshid issue in eks stacks
  • Not overcommitting on ticket story points
  • Better dev testing on no QA required tickets
  • Automation verification is taking a lot of time
  • Barrage of L2s post long holiday leading to SLA slippage

Appreciations

Action Items
  • Setting up time between L2 people each day to work on L2s
  • Third developer for L2s after long weekend 
  • Video recording of working demo as backup
  • Maker time every day inside squad


What did we do well?

What should we have done better?

  • L2s being resolved promptly +3
  • Blockers being resolved in standups +3
  • Good coordination on migration tickets across teams +1
  • Discussed impact in early stages of ticket while testing
  • Availability is less in EKS for migration tickets (Processes getting killed, Memory low)
  • L2s taking a lot of time to resolve
  • Better estimation with buffers
  • Dockers specific to members
  • Many spill over items. To estimate with buffer for analysis and stack issues

Appreciations

Action Items
  • KT on sales360 items to respective squads
  • Add detailed analysis done on L2 (and fix) in the L2/L4 created
  • Add more bandwidth for L2s (Third dev with buffer time to resolve L2s)
  • Having a fixed time of 6pm SLA for L2s? - To check with Preethi


What did we do well?

What should we have done better?

  • Weren't blocked on tickets for long
  • L2 resolutions was good +3
  • Significant progress in migration tickets 
  • Frontend and backend sessions were helpful +1
  • Started migration tickets testing
  • Lifecycle stage ticket was shipped with minimal L4s
  • Better impact capturing during development itself
  • More tickets in ready to test
  • Better estimation - taking into account stack set up, external dependency time etc

Appreciations


Action Items


What did we do well?

What should we have done better?

  • Raising environmental/cross product blockers regularly +1
  • L2s clean board +5
  • Complete migration run attained!! +6
  • All migration tickets in testing
  • Automation false failures reduced drastically 
  • Reduce redundant syncups
  • Estimates could be better (env issues, impact back and forth) +2
  • Facing lot of issues during full migration running. Having to skip the erroring steps +1
  • Issues due to sharing common branch for all migration tickets +1
  • Commits blocked due to FE case failures

Appreciations


Action Items


What did we do well?

What should we have done better?

  • Migration Demo - +7
  • L2 Resolution(No SLA breaches) - +4
  • Ensure ticket contains description and steps to reproduce before grooming meeting. (Finish meeting within stipulated time)
  • Include all the details like relates to (Parent ticket) in the respective tickets and ensure the ticket is in right status
  • Good to always pick up the groomed ticket 
  • Better to add the Technical & Functional details in description rather than comments sections  

Appreciations


Action Items
Ensuring ticket contains all the details like description, Parent ticket, Steps to reproduce and error logs before pulling into sprint


What did we do well?

What should we have done better?

L2's- No SLA Breach + 5

Migration tickets are in good shape +6

CSRF fix +2

Migration tickets needs to be completed within estimated time(Both testing and dev) + 2

If the person is done with the assigned tickets in the sprint, he/she might pick up the ticket that could be a spillover from another person's(in ready for dev status)




Action Items

Celebrate the Migration tickets completion(Moving to prod)

ML Configuration should be in place all the time for at least one stack (1 dedicated ML stack)(BB squad)


What did we do well?

What should we have done better?

  • L2 handled very well + 5
  • Migration issues are fixed in a faster manner
  • KT session went well +1


  • Rspec failures should be handled quickly + 1
  • Most of the tickets were in Ready for staging merge for a longer time due to rspec issues and bcz of staging blocked for reordering components feature
  • Key rotation issue was a blocker
  • Better Planning(Migration has been delayed than the estimated time period )
  • Priority of the tickets needs to be revisited
  • Got many L2s due to Missing Permission - (Inform the corresponding team to run scripts for existing accounts)

Appreciations

L2 - Sivasubramanian Ramar Kishore Shanmugam Praveenkumar Varadan +3

Migrations - Brahmmaeswari Mahalingam Kishore Shanmugam Nivedita Peddiraju

Appreciations for Nivedita Peddiraju  for all her work so far +3

Kishore Shanmugam - Migration KT + L2  +1

Kishore Shanmugam Tamizhselvan R Sivasubramanian Ramar  - Helping out in tickets


Tamizhselvan R  - Finishing all the assigned tickets on time


Action Items

Status of the tickets needs to be updated properly

Rspecs of their BOO  should be owned by the team completely and failures should be fixed faster



What did we do well?

What should we have done better?

Demo went well +4
Testing for Migration tickets are done
Committed items are delivered on time

Migration issues got reduced

L2s  - No SLA breach +1


Frontend tickets assignments

Appreciations

Tamizhselvan R - For his efforts in identifying reasons for Rspec failures +2

Tamizhselvan R - Helping in Debugging of Peer's tickets

Kishore Shanmugam  - For L2s, Assigned tickets along with Import one parallely +3

Praveenkumar Varadan Meenakshi Manikandaswamy - Actively working on L2s +1

Tamizhselvan R Brahmmaeswari Mahalingam  - L2 tickets handling +2

Brahmmaeswari Mahalingam - Demo  +1

Brahmmaeswari Mahalingam Kishore Shanmugam - Migration issues handling


Action Items
Informal meeting for team collaboration
Frontend tickets assignments


What did we do well?

What should we have done better?

L2s went well +2

Migration is stable with no regression issues +1

Migration tasks can be split to the team

Need more frontend task

Need to allocate bandwidth for reviewers - Inform concerned reviewers on their task +2

Bringing frontend folks for grooming

Appreciations

Brahmmaeswari Mahalingam Migration on-time and L2, squad lead  + 3

Meenakshi Manikandaswamy 

Tamizhselvan R L2s +2

Meenakshi Manikandaswamy - Branch automation for migration  +1

Praveenkumar Varadan- Pipeline automation  +1

Pramod Kumar Bollavatni- Helping in picking frontend items

Bhagirath Goud- Managing the squad, resolving blockers +all 

Tamizhselvan Roverall task, l2


Action Items
  1. Getting frontend tasks
  2. Pulling frontend folks in grooming
  3. Frontend review bandwidth from concerned folks
  4. Migration task split up with team
  5. P0/P1 iteration issues in testing should not be identified



What did we do well?

What should we have done better?

  • L2 no SLA breach +4
  • Speaking up in the standup
  • Migration is going great 
  • Team effort is good for migration considering the complexity
  • Missed migration delivery date +2
  • Bulk seeding hiccup
  • Bug fixes for lead score - Dev testing 
  • Some clarity missing for all since migration is different from regular feature

Appreciations



Action Items
  1. Dev testing on p0/p1 test cases
  2. P0/P1 test cases to be shared by the QAs for features and complex US


What did we do well?

What should we have done better?

  • Shipped migration to production - Kudos to team +4
  • Prod migration on sample account +5
  • L2 can be handled better +2
  • Need more proactiveness in L2s 
  • We can observe for few sprints on L2 breach since its exceptional in this sprint +1
  • Find if its critical for customer inspite of being it Low - temporarily unblock for all accounts
  • Track in L4 for fix
  • Redis reinstallation and asset build in EKS 
  • Testing could have been done in chunks during migration

Appreciations

Action Items


What did we do well?

What should we have done better?

  • Migration Bug identification and fixes by the team was great +4
  • L2s went well +2
  • Prod sample account runs +5
  • Clone dependency issue identification +1
  • Standalone migration bugs in prod runs could have been identified - More staging runs +1
  • Focussed testing blocked due to cloning

Appreciations

Migration Bugfixes - Brahmmaeswari Mahalingam Kishore Shanmugam Tamizhselvan R Pramod Kumar Bollavatni +2

Meenakshi Manikandaswamy - Migration Bug identification, Automation false failure fixing +2

Kishore Shanmugam Brahmmaeswari MahalingamProd migration runs, bug fixing +1

Kishore Shanmugam- prod migration runs, L2s documenting issues +1


Action Items
  • L2 handover between devs
  • Waiting on support since long time
  • Bug bash for migration issues in staging by QA


What did we do well?

What should we have done better?

  • L2s handled well +4
  • Demo went successfully +3
  • Production migration runs
  • Bug fixes done quickly
  • Tickets can have more clarity - Confusions on adhoc items during the sprint +1
  • Sprint points can be improved
  • Regression bugs can be avoided 
  • L2s out of scope of BoO need not be checked actively

Appreciations


Action Items

Adding scope and DOD in ticket while planning

Checking with Preethi on reassigned L2s ticket - Sriram Kumar Nagarajan



What did we do well?

What should we have done better?

  • 2 Customer Migrations +2
  • Entire team ramped up and closed bugs
  • Migration code is bug free
  • L2s went well - less incoming L2s
  • Story point delivery is high
  • No spillovers in sprint
  • Sprint planning can have more clarity reducing adhoc items +4

Appreciations

Action Items
  • Sprint planning can have more clarity reducing adhoc items


What did we do well?

What should we have done better?

  • Customer Migration - identified some issues during deployment window +1
  • Less issues in migration +4
  • Less randomised tasks
  • Picking up adhoc items by the team +3
  • Good sprint points and less spillover +2
  • L2s went well +3
  • Performance task for migration
  • Planning can be done better +1
  • Plan for adhoc items +1

Appreciations


Action Items
  • Planning on adhoc items and parking bandwidth


What did we do well?

What should we have done better?

  • Back to back migrations done successfully +4
  • Smooth runs without surprises +4
  • L2s went well +2
  • L2 classification done
  • Adhoc items pulled into sprint +1
  • More precise estimates

Appreciations

Action Items
  • Allocating bandwidth for infra on-call activities.


What did we do well?

What should we have done better?

  • Marathon migration in a sprint by the team +4
  • Not much functional issues in migration runs
  • Not much spillovers in sprint board +1
  • Parallelisation task +1
  • Calculate priorly on customer migration run time and call out +4
  • Allocate more bandwidth in customer runs

Appreciations

Action Items
Reduce pace of migration in-order to accommodate self serve stories
Schedule all migrations in initial part of sprint.
Avoid larger account migrations until done with all parallelisation stories


What did we do well?

What should we have done better?

  • 6 Migrations +2
  • L2 resolution +3
  • Seamless Migrations +1
  • Shipped migration bug fixes
  • Team lunch +1
  • L2 bandwidth should have been allocated more. +2

Appreciations

Kishore Shanmugam Brahmmaeswari Mahalingam Praveenkumar Varadan - L2 resolution

whole team +3

Komal Saraf - understanding of product and migration +2

Praveenkumar Varadan - Mentoring komal

Praveenkumar Varadan - Helping with L2 tickets. +1

Tamizhselvan R - CRM Migration

Action Items
Transparency on Migration Timelines.

Sprints

Support creation and import of accounts with account unique, required fields via contacts import

Epic Details:

Core and Core++ - L2 Tags

Retrospective Action Items

BOO [Digital Sales]:


Session recordings:



Sleeper cells L2 helper scripts 


Members of the Squad:

  1. Bivil Jacob
  2. S A Salai Vinoth 
  3. T Karthik Rajkumar 
  4. Mohit Agrawal
  5. Venkatesan Deivasigamani
  6. Abuthahir Sulaiman 
  7. Parkash Sharma
  8. Suresh Gajendran 
  9. Jaithoonnisha Asif Ali


Our squad mainly focuses on Email, Google Add-on, and Search. 


Team Members

SquadThe Usual Suspects
Engineering Manager
Tech Lead
Squad Lead
Development
Quality Assurance
Product Owner
Squad Emailtheusualsuspects-fsales@freshworks.com

Important Links:

Technical Documents - The Usual Suspects

KT of Freshsales Search Module

Standardising Logs

L2 - FAQ on Emails

Tags for L2 - TUS

Kbase Article Requirements

Existing known issues - TUS (Email, Search and Documents)

TUS L2 Stakeholder Responsibilities

Supreme Scripts for TUS

TUS Sprint History

Onboarding test driven development culture

Central Consumer Implementation Reference

Onboarding KTs for different Modules

Feature Technical Documentation


Squad Members


Sprint Summary:

Sprint NameSprint DurationSpill Over CasesBacklog CasesFalse Failure cases / IT failuresCompleted Cases (Consolidated)Remarks
BBFFPlanned (includes spill over)ActualPlannedActualBacklogFF

Freshsales Reparo Sprint 1

 to  

0063632 BB32632 

23 Cases of old Pending PRs merged to stage.  7 cases dropped

Freshsales Reparo Sprint 2

 to  

5001018830 BB 23945513 cases spilled over
Freshsales Reparo Sprint 3

 to  

136876258 BB + 40 Petta + 23 TUS + 61 HH16415621918 False failures + 25 backlog cases spilled
Freshsales Reparo Sprint 4

 to  

25181339554 BB + 35 Petta+ 30 TUS1192513387 False failures + 38 backlog cases spilled
Freshsales Reparo Sprint 5

 to  

3871278255 BB + 35 Petta+ 30 TUS11333345112 False failures + 43 backlog cases spilled
Freshsales Reparo Sprint 6

 to  

   4612755022721438366525 backlog cases +13 false failures spilled
Freshsales Reparo Sprint 7

 to  

2113210506416383108121 backlog cases+90 false failures spilled
Freshsales Reparo Sprint 8

 to  

2190218





 to  










Sprint NameSprint DurationSpill Over CasesBacklog CasesCompleted Cases (Consolidated)Remarks
Planned (includes spill over)Actual

Freshsales Reparo Sprint 12

 to  

0202122122 


Freshsales Reparo Sprint 13

 to  

80316169291
Freshsales Reparo Sprint 14

 to  

147300199490
Freshsales Reparo Sprint 15

 to  

101312239729
Freshsales Reparo Sprint 16

 to  

73



Freshsales Reparo Sprint 16

 to  







 to  






  • Planned Backlog Cases - Defines the total backlog cases committed by all folks considering the planned leaves and meetings.
  • Planned False Failure cases - Defines the total False failure cases committed by all folks considering the planned leaves and meetings.
  • Actual Backlog Cases -  Defines the total backlog cases merged to staging by all folks.
  • Actual False Failure CasesDefines the total False failure cases merged to staging by all folks.
  • Dropped Backlog CasesDefines the total cases dropped from planned items as it would be already automated or blocker in flow due to bug.
  • Spilled over Cases - Defines the number of Cases not completed in earlier sprint and carried over to current sprint.
  • Completed Cases (consolidated) - Defines the consolidated count on number of cases completed till current sprint.
  • Detailed sheet of specs - This contain the failures IT count



Body of Ownership:

Squad Members:


Squad meetings:

MeetingDay
Stand up

Happens on Monday, Wednesday, and Thursday

Friday - No meeting day

Sprint PlanningHappens in the morning of the first day of Sprint (Tuesday every 2 weeks)
Sprint RetroHappens in the morning of the first day of Sprint (Tuesday every 2 weeks)
Sprint GroomingHappens on the Thursday of the 2nd week of the sprint

L2 Board:

https://freshdeskl2dev.freshdesk.com/a/tickets/filters/search?orderBy=created_at&orderType=desc&q[]=cf_category%3A%5B%22Catalysts%22%5D&ref=727691


Freddy Related Docs:

            Recording:
               
Link: https://freshworks.zoom.us/rec/share/FLrOm9QJM0C2EaqEYIvrRzSrXwq-gwNejJi-G-8TOMGW9JWAJoDe0XVjfbnPcv7f.xoJkKtjjqhqOblEx
               Passcode: aqFwb*y8

EKS stacks:

stacks owned by catalysts k1 to k8.


StackFsales stack branch
Marketplace appsk5k5-marketplace-setup
Rails 4k3integartion_testing_template
Redis point config to push data
from ML
k3
k5
integartion_testing_template
k5-marketplace-setup

 Track stack status: https://docs.google.com/spreadsheets/d/12y5lYCsGk3h9qM5Qy_apLVh4hX4WNN-6lRV8MSxvRAw/edit#gid=0


Catalysts Automation Coverage :

    Current coverage percent - 81%

    Kindly track the automation coverage here → https://confluence.freshworks.com/display/freshsales/Catalysts_Automation+Coverage


Retrospective Action Items:

https://confluence.freshworks.com/display/freshsales/Retrospective+Action+Item+-+Catalyst?src=contextnavchildmode


POC from ML Team:

In case of any ML related queries on our BOO please reach out to, 

Bharathi Balasubramaniam  Saurav Deshmukh Vamseetharan Shyamprasad 


2023 Sprint Summary:


Sprint NameSprint DurationTargeted Story point Achieved Story pointssprint champion 








Others Docs & Links:

        Docs Related to the features moved and developed from catalysts,










BOO

Squad meetings

MeetingDay
Stand up

Happens on Monday, Wednesday and Thursday

Tuesday updates to be commented in slack thread

Friday - No meeting day

Sprint PlanningHappens in the morning of the first day of Sprint (Tuesday for every 2 weeks)
Sprint RetroHappens in the evening of the last day of Sprint (Monday for every 2 weeks)
Sprint GroomingHappens on the Wednesday of the 2nd week on the sprint
Prioritise items for upcoming sprint (IC3s and above)Happens on the Thursday of the 2nd week on the sprint

Squad Members

MemberRole
Engineering Manager
Technical Program Manager
Technical Architect
Staff Product Manager - Product Management
Tech Lead - Frontend
Senior Software Engineer - Backend
Senior Software Engineer - Backend
Senior Software Engineer - Frontend
Software Engineer - Test
Senior Software Engineer - Frontend / Squad Lead
Senior Software Engineer - Backend
Senior Software Engineer - Backend
Senior Software Engineer - Test

Important links:


Body of Ownership:

2023
Q1 OKR -Eagle One Q1 2023-OKR
Q2 OKR- Eagle One Q2 2023-Roadmap
Stability tickets -Stability Tickets

OnCall -Guidelines 


T&D
Home page -FSA - T&D Scope and Roadmap

This document is to help,

  1. Stakeholders understand the various items that Mobile Pod is working on and their Status
  2. Developers refer to all supporting documents in one-place

<Refer - Mobile POD Review for detailed updates on ongoing items>

Table of Contents

1. Ownership

2. Action Items 

Create AI using the ticket type "Action items" and add the tag "podreviewAI"

Action ItemsOwnerFR View


FR Filter

3. OKR Alignment:

FunctionObjectiveKey Result

Current progress/ Status

Product

Improve Unified CRM offering for B2B businesses through Mobile Readiness for sales/field-sales use-cases


  • Support for Arabic UI (Q2)
  • Support for MS Teams (Q2)
  • Advanced in-app notifications (I2P not done yet)
  • Mobile led sign up and onboarding (I2P not done yet, not scope for Q2. Does this have any Engg dependency or only PM driven?)


IN PROGRESS

- PM confirmed it cannot be picked in 2023

Adoption:

Improve adoption from 22% to 30% by end of 2023. (Q2 target 25%) - (Does this have any Engg dependency or only PM driven?)

IN PROGRESS

Current % and what are the epics which are helping adoption

has web dependency so parking it 

Enterprise readiness/GTM transformation

 

  • Prevent past Expected Closed Date on deals (Q2)
  • Role Split in CRUD operation - (Q2)
  • Territory access for custom modules - Q3 (In-Progress)
  • Support for 300+ choices  - (I2P not done yet)
  • Modern Views for Custom Modules - (I2P not done yet)

IN PROGRESS

Manish to update


-reason for deprioritising 

Engineering

Increase crash free users (measured across last 3 app versions for last 30 days)

99% crash free on iOS and Android by end of 2023




IN PROGRESS 

iOS - 98.88% 

Android - 97.93% 

Ensure Engineering Quality

  • On time delivery of roadmap items
  • Meet SLA for High & Urgent L3, L4, Prod bugs & Security bugs
  • Reduce Incoming L4s / Iteration bugs QoQ

IN PROGRESS FR Analytics Report:  https://freshworks.freshrelease.com/reports

FSA Mobile - Prod Bugs / L4s / Security Bugs

Exit Go Lang 

  • iOS - Forms by end of 2023
  • iOS - Filters by end of 2023
  • Android - Other areas apart from filters and forms by end of 2023

iOS - IN PROGRESS

Android - IN PROGRESS

-Filter to be completed for iOS

Exit Objective C in iOS

0 lines of code by end of 2023

IN PROGRESS

Housekeeping for latest OS versions & API levels

(both iOS & Android)

On time adherence to Apple/Google deadlines in 2023

iOS - IN PROGRESS

Android - DONE

FSALES-75956 - Target API level 33 (Android 13)

Improve Star Rating in Store

TBD (PM & Engg to sync up and agree on QoQ Targets)

YET TO START iOS - 4.5 ⭐️ ; Android - 4.69 ⭐️;

Manish to update the stories


4. Roadmap updates

(Items picked for Execution from backlog)

ItemOSSizeDev Start dateDev End Date QA Start Date QA End date Store Upload DateCurrent statusMilestonesComments(Reasons for Delay, Customer feedback, Callouts, Challenges)
Business card scanneriOS XS (spike )

  

 




SPIKE COMPLETED


POC completed .

Android S(spike)

  

 




SPIKE COMPLETED


Spike completes and identified feasible libraries .
POC in progress  
Android Spike: Business card scanner for Freshsales CRM

Collaborators in CSA

FSALES-88263


iOS XS

 13 Nov 

 

22 Nov 



 

DEV COMPLETED


Dev start delay due to Sick leave (Saravanan )

-dev testing in Sprint5

- HH cleared a blocker in dec 14

Android  XS

  

 

  



  



  



DONE


Dev testing on hold due to dependency from HH squad 
- dev testing in sprint 5

Blockers

  1. IRIS blocker with receiving collaborator notifications (Resolved with IRIS folks on-call)
  2. FSALES-94799 Notification payload not inline with existing payload standards

FSALES-88263 has more details about the engineering execution (blockers and observations)

Go lang migration for filter (Tech debt)
FSALES-93412
iOS 

 

Q1 2024




DEV IN PROGRESS



Country code in phone number field

FSALES-96074


iOS 

 





SPIKE IN PROGRESS


Grooming scheduled on Nov 23 

Android  

 





SPIKE IN PROGRESS



FSALES-82978 Deal Value digit incrementiOS S

 

 


Dev testing -  

16 Aug 2023
18 Oct 2023 
31 Oct 2023

 

DONE

  • Dev ETA- Aug 15
  • (Dev testing)QA ETA - 25 Sep
  • Store upload date - 1 Nov

-BE dependent on Rakesh squad due to onboarding items .Get ETA for ETA

BE testing in progress.. (dev testing)Mobile testing started from  

 As discussed on 29 Sep Mobile will go live by (date to be finalised after 3rd oct ) post which matrix team will turn on the flag and fix other fileds to support 16 digits (ETA not confirmed)

Delayed docker received by Matrix squad received on 13 Oct  from 03 Oct



Android S

 

 


Dev Testing -  

16 Aug 2023
18 Oct 2023 
31 Oct 2023

DONE


  • Dev ETA - Aug 9
  • (Dev testing)QA ETA - 25 Sep
  • Store upload date- 6 Nov

-BE dependent on Rakesh squad due to onboarding items 

BE testing inPorgress.. Mobile testing stared from  

- As discussed on 29 Sep Mobile will go live by (date to be finalised after 3rd oct ) post which matrix team will turn on the flag and fix other fileds to support 16 digits (ETA not confirmed).

Delayed docker received by Matrix squad received on 13 Oct  (03 Oct) 

-  ETA moved from 31 Oct to 3 Nov as we have planned to club with custom module release. Also build delivery was delayed by 2 days( Oct 25 to Oct 27)

FSALES-77122 Territory scope for custom modulesiOSXS

 




16 Aug 2023

 

DONE

  • Test run -  
  • QA build ETA - <21/07>  
  • Feature testing ETA -
  • QA Sanity build ETA -  




Web Story for reference FSALES-74809. Territory scope for custom modules

Spike to be picked from 12th, provided docker is available from 9th.

Spike planned in Q2-S6

QA to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.

ETA for ETA-  


-Completed on Sep 1

AndroidXS

 




16 Aug 2023

17 Aug 2023

DONE

  • Test run -  
  • QA build ETA - <21/07>  
  • Feature testing ETA -  
  • QA Sanity build ETA -  

Spike to be picked from 12th, provided docker is available from 9th.

Spike planned in Q2-S6

QA to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.

ETA for ETA-  

- Completed on Aug 17

FSALES-72072 Go Migration & creating a common Forms SDK

(Includes - LCAD, CM, Product, CPQDoc, CSA)

iOSXL

NA




20 Oct 

31 Oct


1 Nov

29 Nov 

DONE

  • Dev ETA - 19 Sep
  • QA ETA - 3 Oct
  • Store upload date- 1 Nov

Refer this confluence for detailed breakup.

Releases planned in multiple milestones, beginning mid May and targeted to complete by end of Q2.

SDK Integration in progress. Will be uploaded by mid-August.


Dev complete by 19 Sep . 8 days of QA effort ETA to be shared+ 3 days final sanity iOS store date 

- QA can start from 3 Oct

- Build rejected due to bug identified by dev and QA was hold.

- Testing is taking time due to more number of cases .ETA moved to ---- from 31 Oct -Ask ramesha

hackathon and we had ipad specific issues & iteration bugs 

 

FSALES-75956 Target API Level 33 (Android 13)AndroidS

NA




28 July 2023

31 Aug 2023 

27 Sep 2023
6 Oct 2023

DONE

  • Dev ETA - July 20
  • Final QA ETA -  27 Sep
  • Store upload date - 6 Oct

20 Sep ETA

27 Sep ETA (merged to staging)

Store upload extended to Oct 5 for L4 completion

FSALES-76597 Go-to-native migration of home screenAndroidM

NA




31 Aug 2023 

6 Oct 2023

18 Oct 2023


31 Dec 2023

DONE

  • Dev ETA - July 20
  • QA ETA - automation and final sanity (based on next release)
  • Store upload date - Dec 19

  Oct 1st week

- on hold due to other items 

- Dev Delay

Reason for delay

Dev responsible for delivery (Anvitha) on notice period -multiple spillovers with PR not being ready for review. 


Final update - PR inconsistencies, bugs and functional issues fixed by Ram and pushed along with Android 3.0

FSALES-75765 Hierarchy based data scopeiOSS

25 Jul 2023 





1 Sep 2023 

DONE

  • Test run ETA -  
  • QA build ETA -  
  • Feature testing ETA -  
  • QA Sanity build ETA -  

Web Story: FSALES-74305
Web Confluence: Territory Hierarchy Honouring CAD modules

Spike to be picked from 12th, provided docker is available from 9th.

Docker is yet to be shared. Spike start date TBD.

Docker will be shared by 7th July

Dev to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.

ETA for ETA-  


Gone live by Sep 1

AndroidS

25 Jul 2023 





27 Sep 2023

6 Oct 2023


DONE

  • Dev ETA - 28 Aug
  • QA start date : 6 Sep
  • QA ETA - 8 Sep
  • Store upload date - 6 Oct

Spike to be picked from 12th, provided docker is available from 9th.

Docker will be shared by 7th July

Dev to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.

ETA for ETA-  

 ETA-20 Sep

ETA- 27 Sep (merged to staging)

 Store upload extended to Oct 5 for L4 completion


FSALES-77137 Auto Assignment of TerritoriesiOSS

 




1 Sep 2023

DONE

  • Test run ETA -  
  • QA build ETA -  
  • Feature testing ETA -  
  • QA Sanity build ETA -  

Web Story for reference FSALES-75274
Auto Assign Primary Territory

Spike to be picked from 12th, provided docker is available from 9th.

Docker will be shared by 7th July

Dev to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.

ETA for ETA-  

gone live by Sep 1

AndroidS

 




27 Sep 2023

6 Oct 2023


DONE

  • Dev ETA - 20 Sep
  • QA start date : 20 Sep
  • QA ETA - 21 Sep
  • Store upload date - 6 Oct

Spike to be picked from 12th, provided docker is available from 9th.

Docker will be shared by 7th July

Dev to be picked in Q3-S2 starting 20th July. Release ETA TBD post planning.

ETA for ETA-  

ETA- Sep 20
ETA- SEP 27 (merged to staging)

 Store upload extended to Oct 5 for L4 completion


Quick Wins 

Mobile : Dowloading/ Saving CPQ Documents as PDF
FSALES-85612

iOSXS

Aug 20

Sep 27

No QA testing - dev testing

no QA testing - dev testing

Oct 6

DONE


aug 17 - aug 30 sprint ---- Dev was completed and release was blocked due to API dependency
Aug 31 - Sep 13 — was on hold 
Sep 14- Sep 27 - merged to staging
Oct 6 - Uploaded to store
Android XS

Sep 14

Sep 27

No QA testing - dev testing

No QA testing - dev testing

Oct 6

DONE


Sep 14- Sep 27

Dev and dev testing completed, merged to staging

Quick Wins 

Mobile: Auto Populate Deal Name


FSALES-85929
iOSXS

Aug 20

Sep 27

No QA testing - dev testing

no QA testing - dev testing

Oct 6

DONE


Was waiting for web release 
Oct 6 - Uploaded to store

Android XS

Sep 14

Sep 27

No QA testing - dev testing

No QA testing - dev testing

Oct 6

DONE


Was waiting for web release 

FSALES-87700

Related sections for Custom Modules in mobile app

iOSS

 

 

No QA testing - dev testing

No QA testing - dev testing

 

DONE

- Q3 2023 S6 -spike

Spike started on Sep 14 - Sep 27 Sprint

Android S

 

 

No QA testing - dev testing

No QA testing - dev testing

31 Oct 2023
 

DONE

 Q3 2023 S6 -spike

Spike started on Sep 14 - Sep 27 Sprint

- Dev (Anvitha) delay in handing over to QA. Store upload date pushed to Nov 6

FSALES-90270Edit File name while uploadingiOSXS

 

 

No QA testing - dev testing

No QA testing - dev testing

 

DONE



AndroidXS

  

 

No QA testing - dev testing

No QA testing - dev testing

 

DONE



Release History

ItemOSSize
Store Upload DatePlanned QuarterDelivered QuarterRelease VersionComments

FSALES-65946  Support Arabic on mobile


iOSM 

 

Q1

Q2

v3.58


AndroidM 

 

Q1

Q2

v2.9.3


FSALES-34619 Roles Enhancements for Call logs (Web parity)iOSS 

Q1

Q2

v3.59


AndroidS 

 

Q1

Q2

v2.9.4


FSALES-71086 Deal - Expected close date cannot be set in the past

iOSXS 

  

Q2

Q2

v3.59


AndroidXS 

 

Q2Q2v2.9.4
FSALES-73669 MS teams for mobile app users

iOSS 

 

Q2

Q2

v3.59


AndroidS 

 

Q2

Q2

v2.9.4


FSALES-75268 Role split for CRUD operations

iOSM 

 

Q2

Q2

v3.60

Web release in July first week.

QA build ETA is delayed by 2 days - had to test in accounts without scope split.

Release date revisited due to QA reduction during Sprint5 (Jun 1st - Jun14th).

AndroidM 

 

Q2

Q2

v2.9.5

Web release in July first week.

QA build ETA is delayed by 4 days - had to test in accounts without scope split, Package Restructure PR to be rev merged.

Release date revisited due to QA reduction during Sprint5 (Jun 1st - Jun14th).

FSALES-76394 Handle Account validation while creation of Accounts from Form, Inline edits
iOSS

 

Q2

Q2

v3.60

Dev Completed.
QA to be picked in Sprint starting 15th June.
QA plan pushed due to QA reduction during Sprint5 (Jun 1st - Jun14th).

AndroidS

 

Q2

Q2

v2.9.5

Dev Completed.
QA to be picked in Sprint starting 15th June.
QA plan pushed due to QA reduction during Sprint5 (Jun 1st - Jun14th).

FSALES-78255 Handle mobile impact of IRIS key rotationAndroidXS 

 

NA

NA

NA


FSALES-78772 List of APIs consumed by mobile with 1-to-many associationsiOSXS 

NA

NA

NA

NA
FSALES-70377 Go Migration - Email ModuleAndroidM 




v.2.9.6
FSALES-77122 Territory scope for custom modulesAndroidS 

 



v2.9.7

5. Crash Status

Firebase Report (last 30 days)21

OS7 Jun21 Jun05 Jul19 Jul20 Sep3 Oct 6 Oct 10 Oct 17 Oct 31 Oct21 Nov 21 Dec
Android97.7%98.03%98.17%97.93%97.38%97.41%97.29%97.36%97.3%97.46% 97.47%98.04 %
iOS98.7%98.96%98.99%98.88%98.84%98.83%98.82%98.79%98.84%98.45% 98.47%98.57 %

Crash Fixes

OSEpicFR#SizeStatusStore Upload DateComments
AndroidFSALES-75905 Q2 Crash Fixes

FSALES-75906

FSALES-82161

XS

DONE

 

Released with v2.9.2

Released with v2.9.5

Android FSALES-82771Q3 Crash Fixes

FSALES-86219



DONE







Not able to reproduce the crash via other flows. Will analyse other touch points and try to reproduce if the crash still happens after the fix  

Android FSALES-90512 Q4 Crash fixes

FSALES-90611


FSALES-92849


DONE


DONE


 

iOSFSALES-77694 Q2 Crash FixesFSALES-77541XS

DONE

 


iOSQ3 Crash FixesFSALES-87394

DONE

 


6. Automation Status

ItemOS04 AugQ3 S2Q3 S3Q3 S4Q3 S5Q3 S6Q4 S1Q4 S3Q4 S5Q4 S6
UT coverageAndroid14.1%20.2%  23.6%24.2%26.8%   
iOS40.2%   40.9%41.9%    
UI Automation CoverageAndroid41.8% (1009/2413)

42.5%
48.05%(1175/2453)48.8%(1213/2485)50.5%(1255/2485)54.8%(1349/2461) 59.3%(1459/2460)
iOS45.35% (1036/2284)

46.2%
50.1%(1150/2298)50.4%(1181/2339)53.4%(1251/2339)55.8%(1309/2343)59.2% (1384/2338)
False failure %Android10.4% (98/942)  11.2%NANA    
iOS6.7% (66/974)   5.5%NA    


AssigneePreplannedPlanned /TargetExecutedSpilled overTarget achieved %Spilled over reasonRemarks 

Q3-S1

Ramesh1313013
Unplanned leave
Mogesh13990


Vyshnavi6660


Nikitha1619613
Unplanned leave

Total4847212644.68 %










Q3-S2

Ramesh2121210


Mogesh1211011
Sick leaves
Vyshnavi1514140


Nikitha1727270



Total6573621184.93 %










Q3-S3

Ramesh16False failures - 43+73False failures - 43+730


Mogesh1517170


Vyshnavi154+10(unplanned)140


Nikitha16SDK false failures5SDK false failures
Additional effort needed

Total6231+116 FF31+116 FF
~90%










Q3-S4
Aug 17-30

Ramesh1236360


Mogesh1618+FF18FF
Gradle upgrade issue
Vyshnavi123021(+2 not feasible, 1 rework testcase)6
Unplanned leave + part 2 took more time(documents)
Nikitha1313+FF13+ SDK FF0



Total5397+FF88+ SDK FF6~90.7%










Q3-S5
Aug 31-Sep 13

Ramesh3539345
Unplanned leave and env setup
Mogesh351046
Other item took time
Vyshnavi3532320


Nikitha35000



Total1408170
86.40%










Q3-S6
Sep 14-29

Ramesh3635350


Mogesh3625210


Vyshnavi3617170


Nikitha3633330



Total144110110
         100%

Q4-S1
Oct 03-18
Ramesh322827(one is is invalid)0
Count is less because Territory Hierarcy tests
Mogesh324835( 8 not applicable)5
Other tickets took more time
Vyshnavi322827(one is invalid)0
Count is less because Territory Hierarcy tests
Nikitha323130( 1 not applicable )0



Total128135 119 596%

Q4-S2
Oct 19 - No 1

Ramesh3287(one invalid)0

Involved in CM revamp testing,
Mogesh3224168


Vyshnavi3216160


Nikitha3220190

involved in iOS SDK automation run

Total1286757885%
QA bandwidth is less because of planned leaves

Q4-S3
Nov 2 - 15

Ramesh(9)403525


Involved in iOS SDK testing in iPad as only I have iPad + pipeline fix
Mogesh(9)402420



Vyshnavi(9)401414



Nikitha(9)402424




Total1809783
 85%

Q4-S4
Nov 16 - Nov 29

Ramesh(9)4030300

Existing files test cases are modified + File rename cases for other modules are added and automated(LAD CM) - 20 new High cases
Mogesh(9)405135(5 out of scope)11
 Sick leave
Anil
241113
Needed time for understanding the framework and pre-defined functions to avoid rework
Vyshnavi(2)1014140


Nikitha(7)32302010
 Sick leave

Total1221491103473.8%

Q4-S5
Nov 30 - Dec 13

Ramesh(9)4031310

Deal name auto create feature automation
Mogesh(9)40482721
cyclone + unplanned leave leave
Vyshnavi(9)40473215
Sick + unplanned leaveDeal name auto create feature automation
Nikitha(9)40554015
cyclone + sick leave

Total1601811305171.8%

Q4-S6
Dec 14 - Dec 27

Ramesh(8)3541392


Mogesh(2)1061556


Anil
41410


Vyshnavi(6)2550455


Nikitha(8)3536360



Total1102292161394.3

7. Adoption

(Manish Srivastava)

FeatureSuccess metrics

Adoption   metrics

Interpretations (Action items to improve adoption)

Heap Dashboard link

Manish Srivastava  - pls add the adoption data available


                          


                                           


https://heapanalytics.com/app/env/2395126988/dashboard/Adoption-iOS-242375


https://heapanalytics.com/app/env/2361584394/dashboard/Adoption-242368

8. Craftsmanship

2023 Trends - Support portal analytics report


Ticket TypeTrends for 12 WeeksInterpretationsFR link for Action items
L1



L2



L3

FD Filter


L4


source - Freshrelease Analytics Report:  → FSA Mobile - Prod Bugs / L4s / Security Bugs

FR Filter


No unresolved L4s

L5

NA
L6



Bugs 



Iteration bugs 



 

Adding new L1/L2/L6 reported in this period - nothing requires immediate attention  

9. L4 + Bugs+Security+Performance

FR Analytics Report: https://freshworks.freshrelease.com/reports → FSA Mobile - Prod Bugs / L4s / Security Bugs

10. Existing prod bugs with other web squads

Filter :

11.Additional details

Q4 Product Backlog

Q3 Product Backlog

Q2 Product Backlog

Pre-planning information

Quarterly Gantt Chart (WIP)

i2p docs master directory (WIP)


Sprint by Sprint - Detailed Info

Retro Action items

Action Items 

QuarterAction itemOwner(s)Current StatusRemarks
Q2 2022Create a Code Review Process Documentation for MobileIn Progress
Q3 2022Come up with a confluence page for all Testcase tagsSenthil Palanisamy Open

RCAs

S.No

Ticket ID & Description

POC

Priority

RCA link

How to avoid going Forward? 

Action Items / Take aways

 Action Item Status

ETA

1










Freshwave Corner


Engineering Tools

This document is to help,

  1. Stakeholders understand the various items that PLG Pod (Asgardians Squad) is working on and their Status
  2. Developers refer to all supporting documents in one-place


POD Team

Squad Name: Asgardians
POD: PLG (Product Led Growth)

Product Management:

Swati Sharma

Niket ChauhanIshita Karbelkar
Product Program Manager

Ramya Raghavan

Engineering ManagerRaghunathan Ravichandran
Back EndThiruvengadam SathiyaseelanFrazer RobertMudhabir 
Front EndJayakumar SrinivasanElavarasan SampathPavithra Perumal
SETVenkat

Likhith


Priyadharshini Chanemougas

Architect - Back EndSivalingam Selvasekaran
Architect - Front EndSaravanan Palani
TPMRavi Sankar


Status Report 

Last Updated on 06.09.2022 11:11  UTC



This page is Archived.
Refer to PLG - New Ways of Working for latest status.


Adoption Metrics


Action Items

S.No

Details

Owner

Update

1



Engineering Corner

Sprint by Sprint - Detailed Info

Refer for Sprint Calendar

Retro Action items


QuarterSprintAction ItemOwnerStatusRemarks (if any)
Q2Asgardians - 2022-Q2-06-20

Consolidated Appcues sheet

https://freshworks.freshrelease.com/ws/FSALES/tasks/FSALES-56049

DoneWill be coming up with a consolidated sheet for future Appcues events
Q2Asgardians - 2022-Q2-06-20Jenkins job failure issue

https://freshworks.freshrelease.com/ws/FSALES/tasks/FSALES-56136

Done
Q2Asgardians - 2022-Q2-07-04Changes/modifications agreed halfway during execution has to be incorporated in mocks then and there itself. Design team has to Own this update. TPM to set the expectations with Design. Ravi Sankar Done
Q2Asgardians - 2022-Q2-07-18Team to ensure Additional code/test case review to be done with BoO TL for changes done in other squads BoOTeamMonitored
Q3Asgardians - 2022-Q3-08-01Team to think and perform Story planning in a way to reduce Spillover possibilities TeamMonitored
Q3Asgardians 




Freshwave 


Templates

Spike Template

Test Plan Template

RCA Template


Point Of Contact's




BOO

Squad meetings

MeetingDay
Stand up

Happens on Monday, Tuesday, Wednesday and thursday

Friday - No meeting day

Sprint PlanningHappens in the morning of the first day of Sprint (Tuesday for every 2 weeks)
Sprint RetroHappens in the evening of the last day of Sprint (Monday for every 2 weeks)
Sprint GroomingHappens on the Wednesday of the 2nd week on the sprint
Story Pointing<TBD>

Squad Members

MemberRole

Position: Engineering Manager
Department: Freshchat

Engineering Manager
Technical Program Manager
Senior Manager - Program Management

Phone: 9677469047
Position: Staff Engineer
Department: FreshChat
Location: Chennai

Technical Architect
Staff Product Manager
Product Manager
Director - Product Management
Software Engineer - Test
Senior Software Engineer - Test
Software Engineer - Backend
Senior Software Engineer
Senior Software Engineer

BOO

Squad meetings

MeetingDay
Stand up

Happens on Monday, Tuesday, Wednesday and thursday

Friday - No meeting day

Sprint PlanningHappens in the morning of the first day of Sprint (Tuesday for every 2 weeks)
Sprint RetroHappens in the evening of the last day of Sprint (Monday for every 2 weeks)
Sprint GroomingHappens on the Wednesday of the 2nd week on the sprint
Story Pointing<TBD>

Squad Members

MemberRole

Position: Engineering Manager
Department: Freshchat

Engineering Manager
Technical Program Manager
Senior Manager - Program Management

Phone: 9677469047
Position: Staff Engineer
Department: FreshChat
Location: Chennai

Technical Architect
Staff Product Manager
Product Manager
Director - Product Management
Software Engineer - Test
Senior Software Engineer - Test
Software Engineer - Backend
Senior Software Engineer
Senior Software Engineer

  • BOO
  • Squad meetings
  • Squad Members
    • Rakesh Kumar
    • Priyanka Balakrishnan
    • Sujitha Ravi
    • Swathi Yerram
    • Brabu Venkatachalam
    • Satya Alasakani
    • Punamalai Muthu
    • Raviteja Kaparapu
    • Savitha Ranganathan
    • Sahithi Yarlagadda
    • Venna Sravani
    • Praveen Kumaravel
    • Lakshmi Padmavathi Nunna
    • Jaisree S B
  • Contacts
  • Shared google drive:

BOO

Pending

TBD

Squad meetings

MeetingDay
Stand up

Happens on Monday, Wednesday and Thursday

Tuesday updates to be commented in slack thread

Friday - No meeting day

Sprint PlanningHappens in the morning of the first day of Sprint (Tuesday for every 2 weeks)
Sprint RetroHappens in the evening of the last day of Sprint (Monday for every 2 weeks)
Sprint GroomingHappens on the Wednesday of the 2nd week on the sprint
Prioritise items for upcoming sprint (IC3s and above)Happens on the Thursday of the 2nd week on the sprint

Squad Members

Contacts

Email: houseofdragons@freshworks.com

Slack: #house-of-dragons

Shared google drive:


Team Members

  1. Karthy Chinnusamy
  2. Komal Saraf
  3. Akshay Desai
  4. Rajalakshmi
  5. Ridwan 
  6. Manikandan C

EM

  1. Sudharshan AJ

TPM

  1. Preethi Mahalingam